<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">

	<head>
		<meta name="copyright" content="Copyright &copy; 2014 The Eclipse Foundation. All Rights Reserved." />
		<meta http-equiv="content-type" content="text/html;charset=UTF-8" />
		<meta http-equiv="Content-Style-Type" content="text/css" />

		<title>Capella - In-Flight Entertainment System - SystemEngineering In&#045;Flight Entertainment System</title>
		<link rel="stylesheet" href="../../scripts/jquery-treeview/jquery.treeview.css" />
  		<script src="../../scripts/jquery-treeview/lib/jquery-1.11.1.js" type="text/javascript"></script>
  		<script src="../../scripts/jquery-treeview/jquery.treeview.js" type="text/javascript"></script>
		<link rel="stylesheet" type="text/css" href="../../css/simpletree.css" />		
		<link title="default" rel="stylesheet" type="text/css" media="screen, projection" href="../../css/content.css"></link>
		<script type="text/javascript">
			if(parent.location.href == self.location.href) {
				window.location.href = 'index.html?8f49452e61f24ba0b944352d1f4c4227' + '#' + self.location.href.substring(self.location.href.lastIndexOf("#")+1);
			}
		</script>
		
		<style>
			body {
				background: white;
				font-family: Arial;
			}
			.treeview {
				background-color: white ;
			}
	
			.treeview ul{ /*CSS for Simple Tree Menu*/
				background-color: white;
				font-size: 12px;
			}
	
			.treeview li{ /*Style for LI elements in general (excludes an LI that contains sub lists)*/
				background-color: white;
			}
		</style>
		
	</head>
	
	<body>	<div id="content">
<img src="../icon/SystemEngineering.png" alt="SystemEngineering" style="float:left; margin-right:10px" /><h1><a href="../In-Flight Entertainment System/8f49452e61f24ba0b944352d1f4c4227.html">In&#045;Flight Entertainment System</a></h1>
<p style="margin-top:3px; margin-bottom:3px"><span class="elementMetaClass">SystemEngineering</span></p>
<em class="elementPath"><a href="../In-Flight Entertainment System/bd182435e29042ceb99f6dd06e7ae7c7.html">In&#045;Flight Entertainment System</a> > <a href="../In-Flight Entertainment System/8f49452e61f24ba0b944352d1f4c4227.html">In&#045;Flight Entertainment System</a></em>

<p>

<p><strong><font size="4">Operational Analysis</font></strong></p>

<p>Several stakeholders have relationships with the IFE system, they all have different goals.&nbsp;The focus is put here&nbsp;on the operational needs the IFE system will somehow contribute to. <strong>What is the precise scope or content of the IFE system is not&nbsp;elicited yet at this stage</strong>.</p>

<p>Discover the entities and their goals in his the operational capabilities diagram: <a href="../In-Flight Entertainment System/58cb491fbea3445baaa605879e858cb7.html#_pmRnML2HEeSzuJ_4_7XgLw">[OCB] Operational Capabilities</a>.</p>

<p>Operational Architecture Diagrams provide a&nbsp;comprehensive view of the activities performed by the entities in order to reach their goals.</p>

<ul>
	<li><a href="../In-Flight Entertainment System/e4e400beb7a340a7b853019a691560fa.html#_xgO34LIUEeSVmfu1BIQISw">[OAB] High-Level Expected Activities</a></li>
	<li>And its refined version <a href="../In-Flight Entertainment System/e4e400beb7a340a7b853019a691560fa.html#_vQXrkLNoEeSVmfu1BIQISw">[OAB] All Operational Activities and Entities</a></li>
</ul>

<p>The different phases of a flight&nbsp;are described in&nbsp;<a href="../In-Flight Entertainment System/c0f768d0034e479584cff4835ed5a790.html#_-czpoPhUEeyYD7A3qrV3tA">[MSM] Aircraft Flying Phases</a> and their sequence in <a href="../In-Flight Entertainment System/d04ae48172c3432eb4e7b2d66264d3b0.html#_VBob4LNqEeSVmfu1BIQISw">[OES] Flight Phases</a>.</p>

<p><font size="4"><strong>System Need Analysis</strong></font></p>

<p>The focus here is put on the IFE system itself. <strong>The objective is to set the boundaries and provide a clear vision of the need</strong>.</p>

<p>The <a href="../In-Flight Entertainment System/7fdc15cd094b4f7cbd926c8d001fb5e7.html#_Q3xl4JTyEeSgObsjQ4XNVQ">[MCB] All Missions and Capabilities</a> diagram&nbsp;shows on the capabilities of the IFE system. Three other diagrams provide interesting entry points to the model:</p>

<ul>
	<li><a href="../In-Flight Entertainment System/e0a467397e504ea6b1980e5efb9ce68f.html#_LzrP8LclEd6PZMYM-Vvo5g">[SC] System Actors</a>&nbsp;lists all the Actors (the aircraft is considered as an actor)</li>
	<li><a href="../In-Flight Entertainment System/411a501a55224fca8b18edbeecb501a1.html#_gaN78KyfEeSJ1PX7slxG4w">[SDFB] Top Level Functional Overview</a>&nbsp;provides a first functional overview of what the actors actually do and what kind of exchanges they have with the IFE system</li>
	<li><a href="../In-Flight Entertainment System/e0a467397e504ea6b1980e5efb9ce68f.html#_xXSwEKv6EeSTJvLsyJitsw">[SAB] Top Level System Overview</a>&nbsp;and its&nbsp;slightly refined version <a href="../In-Flight Entertainment System/e0a467397e504ea6b1980e5efb9ce68f.html#_TGdI0JZDEeS1n7CBuZtEDQ">[SAB] High Level System Overview</a>&nbsp;are <strong>very good entry points to further navigate in the model</strong>.</li>
</ul>

<p>Starting from these high level diagrams,&nbsp;a typical&nbsp;reading path&nbsp;is to dive into the function to visualize their refinement. For example, <a href="../In-Flight Entertainment System/0bfc000cdd3840d39cd32037905a7ab3.html#_Z-lO8LC1EeSAOqSI-4duBg">[SDFB] [CTX] Run Services</a>. And recursively.</p>

<p><strong>Using capabilities as a&nbsp;driver to browse the model is recommended</strong>. Some diagrams are specifically marked for that purpose, for instance <a href="../In-Flight Entertainment System/839ba87384424a01bd1a1f4c3cc6ed52.html#_EsbcMLKzEeSZM9DbsSoyxw">[SDFB] [CAPABILITY] Provide Video Entertainment Services</a>. From this capability covering VOD services to the passengers,&nbsp;browse the functional chains and scenarios to better understand how the capability is fulfilled.</p>

<ul>
	<li>Functional chains: <a href="../In-Flight Entertainment System/e00b45ce330b4b19ac6707095a77f8c0.html#_MOb7kJjJEeSFKIU85IonOQ">[SFCD] Start Playing VOD Movie</a>, <a href="../In-Flight Entertainment System/5ecacd765aa14a9f91f5e00bad983206.html#_m1AKgJjJEeSFKIU85IonOQ">[SFCD] Resume VOD Movie</a></li>
	<li>Scenarios: <a href="../In-Flight Entertainment System/58d8d80a34ab4e60aee2fb8eb885583a.html#_CekP8JWHEeSAToX6gykiew">[ES] Start VOD Service</a>, <a href="../In-Flight Entertainment System/2d18447b6c5a45f78149245290242bab.html#_bkAKcLD-EeSk6sURco8jXw">[ES] Start Playing VOD Movie</a></li>
</ul>

<p>Check the global mode machine of the system with <a href="../In-Flight Entertainment System/1ccc81051b794f8a95e0234f4f4bad6d.html#_ZlrrsPhmEeyYD7A3qrV3tA">[MSM] IFE Operating Modes</a>. Among others, this mode machine is intended to specify under which operational conditions the IFE system is running. Another Mode machine is specifically modelled for what will become the Seat TV: <a href="../In-Flight Entertainment System/f46bd421a0394f23aa32149849966070.html#_ZHdlAPhuEeyYD7A3qrV3tA">[MSM] Seat TV - Movie Player Modes</a></p>

<p><font size="4"><strong>Logical Architecture</strong></font></p>

<p>The Logical Architecture provides an intermediate design, hiding some of the implementation-dependent complexity.</p>

<p>The main architectural drivers&nbsp;are explained in&nbsp;the <a href="../In-Flight Entertainment System/724d6db99175450b8f05023fcffec79c.html#_3blN8KK2Ed6k26nfEmjK4A">[LCBD] Architecture Drivers</a>&nbsp;diagram.&nbsp;&nbsp;Another global view of the logical components is provided by <a href="../In-Flight Entertainment System/724d6db99175450b8f05023fcffec79c.html#_IGYnAKCeEeStTrLYjHtDEw">[LAB] IFE System - All Components, CEs</a></p>

<p>Among others, the refined functional analysis is detailed in the following dataflow diagrams (<a href="../In-Flight Entertainment System/0f580227c543436e979fee70432656e2.html#_1Vd9AK5DEeS_aaAwMjKXtQ">[LDFB] Top Level Functions</a>&nbsp;being an entry point):</p>

<ul>
	<li><a href="../In-Flight Entertainment System/c268e3f13cbc4e628ae275975bc4481f.html#_DHcNsLbMEeS6m7-8Vqqevw">[LDFB] [CTX] Provide Aircraft Interface</a>&nbsp;explains the functional interfacing with the aircraft (the idea being to&nbsp;isolate these functions in an easily replaceable component to ease the integration of the IFE system in different aircrafts)</li>
	<li><a href="../In-Flight Entertainment System/95495bbc987c4b1795d09aa5a87f0344.html#_lekjcK8MEeSUHuFYXP_oBw">[LDFB] [CTX] Manage Audio and Video Diffusion</a>&nbsp;refines&nbsp;how audio&nbsp;and video request&nbsp;are processed.
	<ul>
		<li><a href="../In-Flight Entertainment System/a8452b583135457b8d8559bd23240297.html#_myvsAJvPEeSmFu1YEE0geA">[LDFB] [CTX] Process Audio Video Requests</a>&nbsp;distinguishes between VOD and imposed videos requests</li>
		<li><a href="../In-Flight Entertainment System/d4ee89c8dcf84fa5b2760afa03d409c9.html#_tMgXkJ2JEeSiIpoNkuyYwA">[LDFB] [CTX] Broadcast Stored Audio Video Streams</a>&nbsp;describes the broadcast initialization of content coming from the digital media library</li>
		<li><a href="../In-Flight Entertainment System/cbe07842a67d488abf295b46d3369c15.html#_Lhea0J2eEeSiIpoNkuyYwA">[LDFB] [CTX] Display Video and Play Audio</a>&nbsp;describes how the different media streams are actually rendered</li>
	</ul>
	</li>
</ul>

<p>The allocation of functions to components is exhaustively described in <a href="../In-Flight Entertainment System/724d6db99175450b8f05023fcffec79c.html#_DmXfwKPQEeSgDIOKB3Rd0g">[LAB] [BUILD] Template</a>. Functional&nbsp;chains and scenarios&nbsp;are refined.</p>

<ul>
	<li>Functional chains
	<ul>
		<li><a href="../In-Flight Entertainment System/724d6db99175450b8f05023fcffec79c.html#_nKr5wLeNEeSJrshmHo2mKA">[LAB][CTX] Broadcast Audio Announcement FC</a>&nbsp;(equivalent to <a href="../In-Flight Entertainment System/849047d6233a4f85bf608df1f145cda9.html#_7eoQ4LeJEeSJrshmHo2mKA">[LFCD] Broadcast Audio Announcement</a>)</li>
		<li><a href="../In-Flight Entertainment System/724d6db99175450b8f05023fcffec79c.html#_Hq4jALMDEeSGuvnnapXBhA">[LAB][CTX] Start Playing VOD Movie FC</a>&nbsp; (equivalent to <a href="../In-Flight Entertainment System/24ca4fcd9fe9404c8ce857dd25b038dc.html#_IjNiALFqEeSsWZm7HcO6OQ">[LFCD] Start Playing VOD Movie</a>)</li>
	</ul>
	</li>
	<li>Scenarios
	<ul>
		<li><a href="../In-Flight Entertainment System/2c5abb7e32814651845839d383b9dcc0.html#_FremALbzEeSpk5KlhVegeg">[ES] Perform Audio Announcement</a></li>
		<li><a href="../In-Flight Entertainment System/24e49b35c5574e4fa2a7516009925532.html#_KwN4gLUBEeSkIeuLucFPKA">[ES] Start Playing VOD Movie</a></li>
	</ul>
	</li>
</ul>

<p>A (partial) data model is defined&nbsp;to support the &quot;Start Playing VOD Movie&quot; functional chain. Data and exchanged items are detailed in <a href="../In-Flight Entertainment System/18343c7c222346bca55dc77e1d7c5caf.html#_nlZU8LZ-EeS6m7-8Vqqevw">[CDB] Play Video Movie - Logical</a>.</p>

<p><strong><font size="4">Physical Architecture</font></strong></p>

<p>The Physical&nbsp;Architecture describes how the system will be built.</p>

<p><a href="../In-Flight Entertainment System/5158c7628f3c494798f44cf085492bf5.html#_6Rra8KQUEeSgDIOKB3Rd0g">[PAB] Implementation and Behaviour Components</a>&nbsp;provides an exhaustive view of all physical components. Separate views are available in the breakdown diagrams:</p>

<ul>
	<li><a href="../In-Flight Entertainment System/5158c7628f3c494798f44cf085492bf5.html#_W5gMUKC6EeStTrLYjHtDEw">[PCBD] Implementation Components</a></li>
	<li><a href="../In-Flight Entertainment System/5158c7628f3c494798f44cf085492bf5.html#_o27AcKO1EeSgDIOKB3Rd0g">[PCBD] Behavioural Components</a></li>
</ul>

<p>The allocation of functions to components is exhaustively described in <a href="../In-Flight Entertainment System/5158c7628f3c494798f44cf085492bf5.html#_scrm8LB-EeSflp4pxI7U0A">[PAB] [BUILD] Template</a>. Streaming topics are refined and described in the following dataflow and architecture diagrams:</p>

<ul>
	<li><a href="../In-Flight Entertainment System/cf0384ae550f40a4a8607d081b24a01e.html#_mMpGsLBGEeSnJaHm1OLKKw">[PDFB] [CTX] Broadcast Stored Audio and Video Streams</a></li>
	<li><a href="../In-Flight Entertainment System/d8e4de58aebd43de85d6b7e0011cf619.html#_1EA74LBMEeSnJaHm1OLKKw">[PDFB] [CTX] Play Video Stream on Seat TV</a></li>
	<li><a href="../In-Flight Entertainment System/5158c7628f3c494798f44cf085492bf5.html#_VA5TELPNEeS7E-n173v5iw">[PAB] [CTX] Start Playing VOD Movie FC</a></li>
</ul>

<p>Network topics are only slightly covered in this model.</p>

<ul>
	<li>Usage of REC-RPL mechanisms to replicate network adapters</li>
	<li style="list-style-type: none;">
	<ul>
		<li><a href="../In-Flight Entertainment System/5158c7628f3c494798f44cf085492bf5.html#_xyaY8KYfEeSAVrf1rjnX4A">REC - Unit Network Adapter</a>&nbsp;describes the REC (i.e.what will be replicated)</li>
		<li><a href="../In-Flight Entertainment System/5158c7628f3c494798f44cf085492bf5.html#_BV6mQKYkEeSAVrf1rjnX4A">RPL - Instantiations of Unit Network Adapter</a>&nbsp;describes the three RPLs (replicas).</li>
		<li>The connection between RPLs&nbsp;is detailed in <a href="../In-Flight Entertainment System/5158c7628f3c494798f44cf085492bf5.html#_x1ARYKYIEeSAVrf1rjnX4A">[PAB] Focus on Network Setup, Configuration and Tests</a></li>
	</ul>
	</li>
	<li>The transport of data from one connected equipment to another is described in this diagram: <a href="../In-Flight Entertainment System/5158c7628f3c494798f44cf085492bf5.html#_EWMNsLkaEeSBQ7y8sEdlcw">[PAB] Focus on Network Transport</a></li>
</ul>

<p>The data model related to the &quot;Start Playing VOD Movie&quot; functional chain is refined in <a href="../In-Flight Entertainment System/2ba076cf81ed43f387352205ad26b31c.html#_Snq1oLkiEeSBQ7y8sEdlcw">[CDB] Play Video Movie - Physical</a></p>

<p><strong><font size="4">End-Product Breakdown Structure</font></strong></p>

<p>The EPBS architecture is minimal in this model. The <a href="../In-Flight Entertainment System/fb4d3ed04de743ce9678c3d28e3e44f9.html#_pEpUcLtQEeS87cs0yOXuuQ">[EAB] Configuration Items and Realized Artefacts</a>&nbsp;diagram indicates how physical components, ports and links are allocated to configuration items.</p>

</p>







<h2>Content</h2>
<ul class="generatedList"><li><img src="../icon/OperationalAnalysis.gif" alt="OperationalAnalysis" /> <a href="../In-Flight Entertainment System/e12de7afbf774c439f7c03404be33a29.html">Operational Analysis</a></li><li><img src="../icon/SystemAnalysis.gif" alt="SystemAnalysis" /> <a href="../In-Flight Entertainment System/1d30b780f22247949f785b70ce799bf0.html">System Analysis</a></li><li><img src="../icon/LogicalArchitecture.gif" alt="LogicalArchitecture" /> <a href="../In-Flight Entertainment System/cab89820127c4d24bfe731b2000cc23c.html">Logical Architecture</a></li><li><img src="../icon/PhysicalArchitecture.gif" alt="PhysicalArchitecture" /> <a href="../In-Flight Entertainment System/9a0668cfdb264ee79339c1d8658fa112.html">Physical Architecture</a></li><li><img src="../icon/EPBSArchitecture.gif" alt="EPBSArchitecture" /> <a href="../In-Flight Entertainment System/7c142d0fdd8e4539bcb53ea9c2fdb59d.html">EPBS Architecture</a></li></ul>
















 </div>	</body>
</html>
